Contact alert system and method

ABSTRACT

Embodiments of the present invention are directed to a system and method for receiving transaction data for a transaction, accessing a database comprising alert preference data, generating a contact alert message using the transaction data and alert preference data using a notification server coupled to the database wherein the contact alert message comprises contact information of a first person who conducted the transaction, and sending the contact alert message to a notification device of a second person.

CROSS-REFERENCES TO RELATED APPLICATIONS

This application is a continuation application of U.S. patentapplication Ser. No. 15/463,733, entitled “Contact Alert System andMethod”, filed Mar. 20, 2017, which is a continuation of U.S. patentapplication Ser. No. 12/759,449 entitled “Contact Alert System andMethod”, filed Apr. 10, 2010, which claims the benefit under 35 U.S.C. §119(e) of and is a non-provisional of U.S. Provisional PatentApplication No. 61/237,804, entitled “Contact Alert System and Method,”filed on Aug. 28, 2009, the entire disclosure of which are incorporatedherein by reference for all purposes.

BACKGROUND

Transaction alert messages are used to notify consumers thattransactions have been conducted with their payment cards. For example,a user may receive an alert message regarding a recent transactionconducted at a gas station or with an online merchant. The alert messagemay contain transaction data such as the amount of the transaction, thetime the transaction occurred, and the name of the merchant. The alertmessage may be sent to the user's mobile phone so that the consumer isnotified that a transaction occurred.

Such alert messages could be improved so that they allow differentpersons associated with a payment account to quickly and easilycommunicate with each other.

Embodiments of the present invention address these problems and otherproblems individually and collectively.

BRIEF SUMMARY

Embodiments of the present invention disclosed herein include systemsand methods for sending contact alert messages. The alert system can beimplemented using one or more computer apparatuses and databases.

One embodiment of the invention is directed to a method comprisingreceiving transaction data for a transaction, accessing a databasecomprising alert preference data, generating a contact alert messageusing the transaction data and the alert preference data using anotification server computer wherein the contact alert message comprisescontact information of a first person conducting the transaction, andsending the contact alert message to a notification device used by asecond person.

Another embodiment of the invention is directed to a contact alertsystem comprising a database and a notification server computer coupledto the database. The database stores alert preference data. Thenotification server computer comprises a processor and acomputer-readable medium coupled to the processor. The computer-readablemedium comprises code executable by the processor for implementing amethod comprising: receiving transaction data for a transaction;accessing the database comprising the alert preference data, generatinga contact alert message using the transaction data and alert preferencedata using the notification server computer wherein the contact alertmessage comprises contact information of a first person conducting thetransaction, and sending the contact alert message to a notificationdevice used by a second person.

Another embodiment of the invention is directed to a method comprising:receiving a contact alert message at a notification device used by asecond person after a first person conducts a transaction using aportable consumer device, wherein the contact alert message wasgenerated by a notification server computer coupled to a database usingtransaction data and alert preference data stored in the database. Thecontact alert message comprises contact information for the firstperson. The method further comprises contacting the first person by thesecond person using the notification device that received the contactalert message.

These and other embodiments of the invention are described in furtherdetail below.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 shows a diagram of a alert system.

FIG. 2 shows a portion of the alert system in FIG. 1.

FIG. 3 shows a flowchart illustrating the steps involved in enrollingand updating a consumer in the enrollment database.

FIG. 4 shows a flowchart illustrating the steps involved when a consumerconducts a transaction.

FIG. 5 illustrates a schematic illustration of a contact alert messageaccording to an embodiment of the invention.

FIG. 6 shows a high-level block diagram of a computer apparatus.

FIG. 7A shows a block diagram of a phone.

FIG. 7B shows a diagram of a portable consumer device in the form of apayment card.

DETAILED DESCRIPTION

One embodiment of the invention is directed to a method for sending acontact alert message to a notification device operated by a secondperson regarding a transaction along with contact information of a firstperson that conducted a transaction using a payment card (or other typeof portable consumer device). The contact information in the alertmessage may be in the form of an e-mail address, a phone number, etc.The contact information in the alert message can be selectable, so thatthe notification device that receives the contact information can beused to readily contact the first person via the first person'snotification device.

Illustratively, a first person such as a teenage son in a household maypurchase an item at a merchant using a payment card, and a generaltransaction alert message may be sent to the son's mobile phone. Thegeneral transaction alert message may contain transaction data includingthe amount of the transaction, the merchant's name, and an identifierfor the payment card. In addition to the general transaction alertmessage, a contact alert message may be sent to a mobile phone operatedby the son's father (i.e., the second person). In addition to thetransaction data, the contact alert message may also contain the phonenumber associated with the son's mobile phone. The phone number is inthe form of an active link that can automatically dial the mobile phonenumber of the son's mobile phone when the active link is selected (e.g.,touched). When the son conducts the transaction, the father is notifiedas to what the son is purchasing substantially contemporaneously (e.g.,within 5 or 1 minute or less) with the son's purchase. If the fatherwants to contact the son, the father can simply touch the phone numberin the contact alert message.

The second person may want to contact the first person for a variety ofreasons. In the example above, the father may want to contact the son toask the son why he is conducting the transaction. The father mayalternatively want to ask his son to purchase another item at that samemerchant, or at another merchant nearby.

I. Systems

FIG. 1 is a diagram illustrating an alert system 100, in accordance withan embodiment of the invention. The alert system 100 includes a firstperson 110, a second person 211, a portable consumer device 120, amerchant 130, an access device 132, an acquirer 140, a paymentprocessing network 150, an issuer 160, an IP gateway 170, mobile devicecarriers 190, e-mail servers 180, a mobile device 200, a user computer210, and Web services 220. The mobile device 200 and the user computer210 are examples of notifications devices. Further descriptions ofnotification devices and portable consumer devices are provided below.

First person 110 uses the portable consumer device 120 to conduct atransaction, and may further operate a mobile device 200 such as amobile phone. The mobile device 200 operated by the first person 110 mayreceive a general transaction alert message after the first person 110conducts a transaction using his portable consumer device 120.

Merchant 130 has an access device 132 for interacting with the portableconsumer device 120 and the acquirer 140 is associated with the merchant130. Acquirer 140 is in communication with issuer 160 through paymentprocessing network 150.

The alert system 100 also includes an IP gateway 170 that is incommunication with payment processing network 150. IP gateway 170receives the transaction data from the payment processing network 150and generates transaction alert messages. IP gateway 170 is also incommunication with the mobile device carriers 190, e-mail servers 180,and Web services 220. The mobile device carriers 190 are in operativecommunication with the mobile device 200, and the mail servers 180 arein operative communication with the user computer 210. The transactionalert messages that are generated from IP gateway 170 are sent to themobile device carriers 190 and/or mail servers 180 to be sent to themobile device 200, and/or the user computer 210.

Web services 220 is also in operative communication with the secondperson 211 for enrolling the second person 211 and the first person 110in the messaging service provided by the alert system 100. Web services220 may also be in communication with a merchant 130 for enrollingmerchant 130 in the messaging service provided by the alert system 100.

The first person 110 and the second person 211 may each be an individualor organization such as a business that is capable of purchasing goodsor services or conducting any suitable transaction with the merchant130.

Merchant 130 may refer to any suitable entity or entities that canconduct a transaction with first person 110 and/or the second person211. Merchant 130 may have a physical location which sells goods andservices to the first person 110 or the second person 211. For example,merchant 130 may use an e-commerce business to allow the transaction tobe conducted by merchant 130 through the Internet. Other examples ofmerchant 130 include a department store, a gas station, a drug store, agrocery store, or other suitable business.

Access device 132 may be any suitable device for communicating withmerchant 130 and for interacting with portable consumer device 120.Access device 132 can be in any suitable location such as at the samelocation as merchant 130. Access device 132 may be in any suitable form.Some examples of access devices 132 include POS devices, cellularphones, PDAs, personal computers (PCs), tablet PCs, hand-heldspecialized readers, set-top boxes, electronic cash registers (ECRs),automated teller machines (ATMs), virtual cash registers (VCRs), kiosks,security systems, access systems, Websites, and the like. Access device132 may use any suitable contact or contactless mode of operation tosend or receive data from portable consumer devices 120.

If access device 132 is a POS terminal, any suitable POS terminal may beused and may include a reader, a processor, and a computer-readablemedium. Reader may include any suitable contact or contactless mode ofoperation. For example, exemplary card readers can include radiofrequency (RF) antennas, optical scanners, bar code readers, magneticstripe readers, etc. to interact with portable consumer device 120.

Acquirer 140 refers to any suitable entity that has an account withmerchant 130. In some embodiments, issuer 160 may also be acquirer 140.

Payment processing network 150 refers to a network of suitable entitiesthat have information related to an account associated with portableconsumer device 120. This information includes data associated with theaccount on portable consumer device 120 such as profile information,data, and other suitable information.

Payment processing network 150 may have or operate a server computer andmay include a database. The database may include any hardware, software,firmware, or combination of the preceding for storing and facilitatingretrieval of information. Also, the database may use any of a variety ofdata structures, arrangements, and compilations to store and facilitateretrieval of information. The server computer may be coupled to thedatabase and may include any hardware, software, other logic, orcombination of the preceding for servicing the requests from one or moreclient computers. The server computer may use any of a variety ofcomputing structures, arrangements, and compilations for servicing therequests from one or more client computers.

Payment processing network 150 may include data processing subsystems,networks, and operations used to support and deliver authorizationservices, exception file services, and clearing and settlement services.An exemplary payment processing network 150 may include VisaNet™.Networks that include VisaNet™ are able to process credit cardtransactions, debit card transactions, and other types of commercialtransactions. VisaNet™, in particular, includes a VIP system (VisaIntegrated Payments system) which processes authorization requests and aBase II system which performs clearing and settlement services. Paymentprocessing network 150 may use any suitable wired or wireless network,including the Internet.

Issuer 160 refers to any suitable entity that may open and maintain anaccount associated with portable consumer device 120 used by firstperson 110 and/or the second person 211. Some examples of issuers may bea bank, a business entity such as a retail store, or a governmentalentity.

IP gateway 170 refers to an entity that generates and deliversnotifications and contact alert messages to various delivery channels.IP gateway 170 may include one or more servers and databases forgeneration of the contact alert messages and retrieval of data. IPgateway 170 may be part of the payment processing network 150 or may bea separate entity in communication with payment processing network 150.

E-mail servers 180 are server computers configured to receive an e-mailfrom a network connection and store the e-mail in memory for futureretrieval.

Mobile device carriers 190 refer to entities that provide wirelessinfrastructures for wireless data transfer and communication viacellular phone or other mobile devices. Example of such entities areAT&T™, Verizon Wireless™, T-Mobile™, etc.

Mobile device 200 may be in any suitable form. For example, suitablemobile device 200 can be hand-held and compact so that they can fit intoa consumer's wallet and/or pocket (e.g., pocket-sized). Some examples ofmobile device 200 include desktop or laptop computers, cellular phones,personal digital assistants (PDAs), pagers, payment cards, securitycards, access cards, smart media, transponders, and the like. In someembodiments, mobile device 200 and portable consumer device 120 areembodied in the same device. In some embodiments, the mobile device 200(or other notification device) may comprise a processor, and a computerreadable medium coupled to the processor. The computer readable mediumcomprises code, executable by the processor, for implementing a methodcomprising: receiving a contact alert message at a notification deviceused by a second person after a first person conducts a transactionusing a portable consumer device, wherein the contact alert message wasgenerated by a notification server computer coupled to a database usingtransaction data and alert preference data stored in the database,wherein the contact alert message comprises contact information for thefirst person; and contacting the first person by the second person usingthe notification device that received the contact alert message.

User computer 210 may be a personal computer or a laptop. The Usercomputer 210 may run an operating system such as Microsoft Windows™ andmay have a suitable browser such as Internet Explorer™.

Web services 220 may be in the form of a server and a Website whichallows users and merchants to enroll in the messaging service. Webservices 220 may be provided by the issuer 160 or the payment processingnetwork 150.

FIG. 2 is a diagram illustrating a subsystem 101 of the alert system100. FIG. 2 illustrates more details about the IP gateway 170. The IPgateway 170 includes a notification server computer 171. Thenotification server computer comprises a processor and acomputer-readable medium 172 coupled to the processor (not shown). Thecomputer readable medium comprises code executable by the processor forimplementing a method comprising: receiving transaction data for atransaction; accessing the database comprising alert preference data;generating a contact alert message using the transaction data and alertpreference data using the notification server computer wherein thecontact alert message comprises contact information of a first personconducting the transaction; and sending the contact alert message to anotification device used by a second person.

The notification server computer 171 is in communication with a database173. In some embodiments, database 173 may be included in thenotification server computer 171. Database 173 contains transaction data174, issuer data 175, and consumer enrollment data 176 (which mayinclude alert preference data). Consumer enrollment data 176 aresynchronized with the enrollment database 152 in the payment processingnetwork 150 via the synchronization link 156. The enrollment database152 contains data related to persons who are enrolled in the messagingservice. As shown in FIG. 2, IP gateway 170 is in communication withpayment processing network 150, and Web services 220 via the networkconnection 154 which may be in any suitable form. The network connection154 may include, for example, at least a portion of the Internet.Delivery channel logic 182 is in communication with IP gateway 170,mobile service carriers 190, e-mail servers 180, and other deliverychannels 186.

II. Methods

A. Enrollment

In order to receive the contact alert messages associated with atransaction, a second person 211 enrolls in the messaging serviceprovided by the alert system 100.

There may be multiple ways in which second person 211 may becomeenrolled in the messaging service. In some embodiments, second person211 may be enrolled automatically by the issuer 160 that issues theportable consumer device 120. Enrollment for a consumer such as thesecond person 211 may also be done in a batch mode, by file deliveryfrom issuer 160 or by file delivery from some other party. In otherembodiments, issuer 160 or payment processing network 150 may providethe messaging service as an option to second person 211 at which timesecond person 211 may enroll in the messaging service either bycontacting a customer service representative over the phone (providedeither by issuer 160 or payment processing network 150), or by accessinga Web site and filling out an online application.

During the enrollment process either by accessing a Web site and fillingan online application or by contacting a customer service, second person211 can add new persons or update existing persons associated with thepayment account held by the second person 211. For each personassociated with the account, the second person can provide informationfor that person, such as name, mobile device information, cardidentification, and contact information, etc. For example, the father ina family may be the second person and may be a primary account holder ofan account associated with a payment card. The father may then enrollthe mother and his teenage son in the service. Either the mother or theson may be a second person. The father may provide the mother andteenage son's mobile phone numbers during the enrollment process. Aswill be described in further detail below, the alert system 100 thenuses this data along with transaction data to generate and deliver thecontact alert messages. The second person 211 may access the Web site orcontact the issuer 160 to change his information at any time.

FIG. 3 illustrates an exemplary process where second person 211 createsand/or updates his user profile through enrollment process. Secondperson 211 first needs to log into the enrollment system by providinghis login ID and password (step 310). After second person 211 inputs hislogin ID and password, the login ID and password are then validatedagainst the data in the database. If the second person's logininformation is validated, he may either add or update a personassociated with the account.

In certain embodiments of the invention, the second person may havemultiple persons on the account. Each person associated with the accounthas a portable consumer device 120. The portable consumer device 120contains the account number and a device identifier associated with thataccount number. In one embodiment, the second person 211 may add a newperson (such as first person 110) to his account (step 330). An emptyform can be displayed on the Web site for the second person 211 to fillin the information for the new person (step 332). In one embodiment ofthe invention, the fields for the second person 211 to fill in includethe name of the person, the portable consumer device's identifier (step334), and information regarding the second person's mobile device 200,such as the make and model number of the mobile device 200, and theentity that is the carrier for wireless service of that mobile device200. Second person 211 then fills in the forms with the appropriateinformation (step 336), and submits the change for the enrollment systemto update the database with the information that the second person 211provided (step 350).

In one embodiment, second person 211 may update an existing person ofhis account (step 340). The enrollment system sends a query to thedatabase to retrieve the information for that person. A form prefilledwith the those information will be displayed on the Website for thesecond person 211 to update the information (step 342). Second person211 then updates information, such as the identifier of the portableconsumer device for the first person (step 344), and contact information(such as phone number of the mobile device) (step 346), and submits thechange for the enrollment system to update the database with theinformation the consumer provided (step 350).

In one embodiment, the second person 211 may also set some other alertpreferences, such as the language preference and preferred deliverychannels of the contact alert message. For example, second person 211may specify during the enrollment process that he would like to receivethe contact alert messages in a particular language. Second person 211may also specify who would receive the contact alert message when aperson is conducting a transaction. In one embodiment, consumer mayselect one or more persons to receive the contact alert message. Secondperson 211 may also specify whether the alert message will be sent to aperson on his mobile device 200, or at a particular e-mail address.

The information that the consumer 110 provides is stored in the database173 in the form of consumer enrollment data 176, as shown in FIG. 2. Thedata, sometimes referred to as alert preference data, in addition to thetransaction data 174 and issuer data 175, is used by the notificationserver computer 171 to generate the contact and general transactionalert messages.

B. Conducting a Transaction

FIG. 4 shows a flow diagram of steps involved after conducting atransaction according to an embodiment of the invention. In a typicalpurchase transaction, a first person 110 purchases goods or services atmerchant 130 using the portable consumer device 120 (arrow 1 in FIG. 1,step 410). An authorization request message comprising transaction datais generated by a processor in the access device 132 after the portableconsumer device 120 interacts with the access device 132. Theauthorization request message may comprise, for example, the BIN (bankidentification number) and expiration date associated with the portableconsumer device 120, the purchase amount, and a merchant code such as amerchant category code (MCC). The authorization request message is thenforwarded from the merchant 130 to the acquirer 140 (arrow 2 in FIG. 1).After receiving the authorization request message, acquirer 140 thensends the authorization request message to the payment processingnetwork 150 (arrow 3 in FIG. 1, step 415).

The payment processing network 150 then forwards the authorizationrequest message to the issuer 160 (arrow 4 in FIG. 1, step 420). Afterthe issuer 160 receives the authorization request message, the issuer160 sends an authorization response message back to the paymentprocessing network 150 to indicate whether or not the currenttransaction is authorized (or not authorized) (arrow 5 in FIG. 1).

After the payment processing network 150 receives the authorizationresponse message (step 425), it then forwards the authorization responsemessage to the acquirer 140 (arrow 6 in FIG. 1). The acquirer 140 thensends the authorization response message to merchant 130 (arrow 7 inFIG. 1), and it is then presented to the first person 110 (arrow 8 inFIG. 1).

If the account for the first person 110 and the second person 211 isenrolled in the contact alert messaging service, payment processingnetwork 150 sends the transaction data to IP gateway 170 (arrow 6 b inFIG. 1). In order for payment processing network 150 to determinewhether the transaction is associated with a portable consumer device120 that is enrolled in the contact alert messaging service, paymentprocessing network 150 maintains a list of account numbers associatedwith consumers who are enrolled in the contact alert messaging servicein the enrollment database 152. The data in the enrollment database 152are synchronized with the appropriate portion(s) of the consumerenrollment data 176 via synchronization link 156 which may be in anysuitable form. For example, the synchronization link 156 may be in theform of local area network connection or Internet.

After IP gateway 170 receives the transaction data 174 from paymentprocessing network 150 (step 430), the notification server computer 171begins the process of generating a contact alert message for thattransaction. During this process, regular processing for transactionauthorization continues as normal with the issuer, while at the sametime the transaction is inspected and compared to pre-establishedselected triggers and preferences. The contact alert message isgenerated and is delivered in real time or near real time to thenotification device operated by the second person 211. Many times, thecontact alert message is received before the first person 110 leaves acheckout counter at the merchant 130 (e.g., within 5 minutes after thetransaction starts).

The transaction data 174 received from the payment processing network150 contains information such as an account number and an identifierassociated with the portable consumer device 120, name of the merchant130, a merchant identifier such as a merchant category code or MCC, atransaction identifier and the amount of the transaction. Thetransaction data 174 may also contain other information such as thelocation of the merchant 130. In one embodiment, the transaction data174 may be stored in database 173. In other embodiments, the transactiondata 174 may be sent directly to the notification server computer 171.

After receiving the transaction data 174, the notification servercomputer 171 analyzes the transaction data. Certain data elements in thetransaction data 174 are extracted, such as the account numberassociated with the portable consumer device 120, the portable consumerdevice identifier and merchant identifier. The notification servercomputer 171 then accesses database 173 to retrieve alert preferencedata based on values of these data elements. At step 435, thenotification server computer 171 accesses consumer enrollment data 176in database 173 to retrieve the contact information of the second person211 based on the account number and the identifier of the portableconsumer device 120.

In some embodiments, the notification server computer 171 may alsoretrieve the issuer data. The issuer data may include, the name andaddress of the issuer, a phone number to contact, and the issuer's logo,etc. In one embodiment, the issuer data may be stored in the database173. In another embodiment, the issuer data may reside in a remotedatabase. In still another embodiment, the issuer data may be sent tothe IP gateway 170 by the payment processing network 150. The issuerdata may be used in generating an alert message.

The notification server computer 171 may also access other resources tofurther enhance the contact alert messages. These resources may be inthe form of translation tables or reference tables for abbreviations andsymbols. Such resources may be part of the database 173, be stored innotification server computer 171, or be stored in a remote location. Insome embodiments, the contact alert messages are translated into alanguage spoken by the consumer 110. During the enrollment process, theconsumer 110 may be provided with the option of receiving the contactalert messages in his native language.

After accessing the alert preference data and determining the technicalrequirements and consumer and merchant preferences, the notificationserver computer 171 generates a contact alert message and a generalalert message (step 440). The alert message generation is performed by aprocessor using a software application stored in the computer readablemedium 172 that is running on the notification server computer 171. Inone embodiment, some functions may be performed by an ApplicationSpecific Integrated Circuit (ASIC) that may be part of the notificationserver computer 171. In some other embodiments, the contact alertmessages may be generated by the combination of software applicationsand ASICs.

FIG. 5 shows an exemplary contact alert message 500 sent to the secondperson 211. In certain embodiments of the invention, the contact alertmessage 500 provides the alert sender information 510 so that therecipient of the message can identify the sender of the alert message.For example, the alert message 500 may contain the name and address ofthe sender. The contact alert message may also contain the phone numberof the sender so that the second person may contact the sender. Incertain embodiments, a contact alert message 500 may include a logo 520of the sender, further identifying the sender.

The contact alert message 500 may also include account information 530to identify the account involved in the transaction. The accountinformation on the alert message may clearly identify the accountassociated with the transaction. In one embodiment, the accountinformation on the alert does not include the full and complete accountnumber in order to protect the information if the alert message evergets lost. For example, an alert message may use a phrase “CRD 72” toidentify a credit card account which ends in 72.

In certain embodiments, the main body 540 of a contact alert message 500comprises text. The text could include any information regarding theassociated transaction. For example, the text may be: “There is a chargeof $20.00 on your credit card ending with 72 at the Walmart™ store inMountain View, Calif.” Various tables of different specific messages ormessage templates may be used to generate a contact alert message. Forexample, a message template indicating a grocery store might be “Youpurchased $[insert purchased amount] of groceries at $[insert storename] in $[insert store location].”

In certain embodiments of the invention, the contact alert message 500contains the name of the first person who conducted the transaction 544,and/or the contact information of the first person 546. The contactinformation may be in the form of a phone number or other address(e-mail address), which is immediately selectable by the second person.When the second person selects the contact information, the device thatis displaying the contact information may automatically call the firstperson that is associated with the contact information and that isconducting the present transaction.

In some embodiments, the notification server computer 171 may alsogenerate a general alert message to send to the first person 110 whoconducted the transaction. Unlike the contact alert message that is sentto the second person, the general alert message does not include thename and contact information of the first person. Other attributes ofthe general alert message may be similar to those shown in FIG. 5. Thus,in embodiments of the invention, at least two alert messages withdifferent content may be sent to two different persons.

In situations where the notification server computer 171 generates alertmessages for a transaction based on the preference of more than onedelivery channels, each message may be customized based on criteria andrequirements of each of the delivery channels. For example, if onecontact alert message is being sent to the mobile device 200 in the formof a text message, and another one to the user computer 210 in the formof an e-mail, the notification server computer 171 may include moregraphics and data in the e-mail message. In some embodiments, issuer 160may have different logo formats for use with different deliverychannels.

When an alert message is generated by the notification server computer171, it is sent to the delivery channel logic 182 for delivery toconsumer 110 (arrows 6 b in FIG. 1). The delivery channel logic 182 maybe in the form of one or more software applications running on one ormore computers that are tasked with delivery of the contact alertmessages to the appropriate delivery channel. In one embodiment, thedelivery channel logic may be part of the IP gateway 170. In anotherembodiment, the delivery channel logic 182 may be a third party entitythat receives the contact alert message via network connection 154 andsends it to an appropriate user device.

In one embodiment, the alert messages may be sent along with anindicator that specifies what form of delivery channel should be usedfor the delivery of the message. The notification server computer 171retrieves the indicator from enrollment database. Delivery channel logic182 is in communication with mobile device carriers 190 and e-mailservers 180, for sending the contact alert messages in formats that arereadable by the mobile device 200, and in the form of e-mail messagesthat are readable by user computer 210.

In one embodiment, the notification server computer 171 retrieves theinformation of the second person 211 that is supposed to receive thecontact alert message, from the enrollment database (step 445). Thisinformation includes name of the second person and mobile device 200information of the second person (step 450). The notification servercomputer then sends the contact alert message to the second person'smobile device 200 (step 455).

In another embodiment, the notification server computer 171 retrievesthe mobile device information of the first person so that a generalalert message can be sent to him (step 470). The notification servercomputer 171 then sends the general alert message to the first person'smobile device 200 (step 475). In some embodiments, an alert message maybe sent to a user in the form of Interactive Voice Response (IVR),Instant Message (IM), voicemail, etc.

In some embodiments, the delivery channel logic 182 or the notificationserver computer 171 may cause the mobile device 200 to play an specialaudio file with a sound of a “beep” when receiving an alert message(steps 460, 480). In embodiments where the second person receives acontact alert message regarding a transaction conducted by the firstperson, once the second person is alerted of the transaction, the secondperson may contact the first person using the contact informationprovided in the contact alert message.

III. Portable Consumer Devices and Computer Apparatuses

The various participants and elements in FIGS. 1 and 2 may operate oneor more computer apparatuses to facilitate the functions describedherein. Any of the elements in FIGS. 1 and 2 may use any suitable numberof subsystems to facilitate the functions described herein. Examples ofsuch subsystems or components are shown in FIG. 6. The subsystems shownin FIG. 6 are interconnected via a system bus 645. Additional subsystemssuch as printer 644, keyboard 648, fixed disk 649, monitor 646, which iscoupled to display adapter 682, and others are shown. Peripherals andinput/output (I/O) devices, which couple to I/O controller 641, can beconnected to the computer system by any number of means known in theart, such as serial port 684. For example, serial port 684 or externalinterface 681 can be used to connect the computer apparatus to a widearea network such as the Internet, a mouse input device, or a scanner.The interconnection via system bus 645 allows a central processor 643 tocommunicate with each subsystem and to control the execution ofinstructions from system memory 642 or fixed disk 649, as well as theexchange of information between subsystems. The system memory 642 and/orfixed disk 649 may embody a computer readable medium.

FIGS. 7A-7B show block diagrams of portable computer devices andsubsystems that may be present in computer apparatuses in systemsaccording to embodiments of the invention.

The portable consumer device 32 may be in any suitable form. Forexample, suitable portable consumer devices can be hand-held and compactso that they can fit into a consumer's wallet and/or pocket (e.g.,pocket-sized). They may include smart cards, ordinary credit or debitcards (with a magnetic strip and without a microprocessor), keychaindevices (such as the Speedpass™ commercially available from Exxon-MobilCorp.), etc. Other examples of portable consumer devices includecellular phones (e.g., the phone 34 described above), personal digitalassistants (PDAs), pagers, payment cards, security cards, access cards,smart media, transponders, and the like. The portable consumer devicescan also be debit devices (e.g., a debit card), credit devices (e.g., acredit card), or stored value devices (e.g., a stored value card).

An exemplary portable consumer device 32′ in the form of a phone maycomprise a computer readable medium and a body as shown in FIG. 7A.(FIG. 7A shows a number of components, and the portable consumer devicesaccording to embodiments of the invention may comprise any suitablecombination or subset of such components.) The computer readable medium32(b) may be present within the body 32(h), or may be detachable fromit. The body 32(h) may be in the form a plastic substrate, housing, orother structure. The computer readable medium 32(b) may be a memory thatstores data and may be in any suitable form including a magnetic stripe,a memory chip, uniquely derived keys (such as those described above),encryption algorithms, etc. The memory also preferably storesinformation such as financial information, transit information (e.g., asin a subway or train pass), access information (e.g., as in accessbadges), etc. Financial information may include information such as bankaccount information, bank identification number (BIN), credit or debitcard number information, account balance information, expiration date,consumer information such as name, date of birth, etc. Any of thisinformation may be transmitted by the portable consumer device 32.

Information in the memory may also be in the form of data tracks thatare traditionally associated with credits cards. Such tracks includeTrack 1 and Track 2. Track 1 (“International Air Transport Association”)stores more information than Track 2, and contains the cardholder's nameas well as account number and other discretionary data. This track issometimes used by the airlines when securing reservations with a creditcard. Track 2 (“American Banking Association”) is currently mostcommonly used. This is the track that is read by ATMs and credit cardcheckers. The ABA (American Banking Association) designed thespecifications of this track and all world banks must abide by it. Itcontains the cardholder's account, encrypted PIN, plus otherdiscretionary data.

The portable consumer device 32 may further include a contactlesselement 32(g), which is typically implemented in the form of asemiconductor chip (or other data storage element) with an associatedwireless transfer (e.g., data transmission) element, such as an antenna.Contactless element 32(g) is associated with (e.g., embedded within)portable consumer device 32′ and data or control instructionstransmitted via a cellular network may be applied to contactless element32(g) by means of a contactless element interface (not shown). Thecontactless element interface functions to permit the exchange of dataand/or control instructions between the mobile device circuitry (andhence the cellular network) and an optional contactless element 32(g).

Contactless element 32(g) is capable of transferring and receiving datausing a near field communications (“NFC”) capability (or near fieldcommunications medium) typically in accordance with a standardizedprotocol or data transfer mechanism (e.g., ISO 14443/NFC). Near fieldcommunications capability is a short-range communications capability,such as RFID, Bluetooth™, infra-red, or other data transfer capabilitythat can be used to exchange data between the portable consumer device32′ and an interrogation device. Thus, the portable consumer device 32′is capable of communicating and transferring data and/or controlinstructions via both cellular network and near field communicationscapability.

The portable consumer device 32′ may also include a processor 32(c)(e.g., a microprocessor) for processing the functions of the portableconsumer device 32′ and a display 32(d) to allow a consumer to see phonenumbers and other information and messages. The portable consumer device32′ may further include input elements 32(e) to allow a consumer toinput information into the device, a speaker 32(f) to allow the consumerto hear voice communication, music, etc., and a microphone 32(i) toallow the consumer to transmit her voice through the portable consumerdevice 32. The portable consumer device 32′ may also include an antenna32(a) for wireless data transfer (e.g., data transmission).

If the portable consumer device is in the form of a debit, credit, orsmartcard, the portable consumer device may also optionally havefeatures such as magnetic strips. Such devices can operate in either acontact or contactless mode.

An example of a portable consumer device 32″ in the form of a card isshown in FIG. 7B. FIG. 7B shows a plastic substrate 32(m). A contactlesselement 32(o) for interfacing with an access device 34 may be present onor embedded within the plastic substrate 32(m). Consumer information32(p) such as an account number, expiration date, and consumer name maybe printed or embossed on the card. Also, a magnetic stripe 32(n) mayalso be on the plastic substrate 32(m).

As shown in FIG. 7B, the portable consumer device 32″ may include both amagnetic stripe 32(n) and a contactless element 32(o). In otherembodiments, both the magnetic stripe 32(n) and the contactless element32(o) may be in the portable consumer device 32″. In other embodiments,either the magnetic stripe 32(n) or the contactless element 32(o) may bepresent in the portable consumer device 32″.

Embodiments of the invention have a number of advantages. For example,embodiments of the invention can alert a second person of a transactionthat a first person is conducting using a contact alert message. One ofthe benefits of receiving alert messages of transactions conducted by afirst person, by the second person, is that the second person is madeaware of where the first person is at any given moment. If the secondperson is made of aware of where the first person is and what the firstperson is purchasing, then the second person can easily contact thefirst person shortly after the first person has conducted a transaction.The second person can ask the first person where he or she is, why theyare conducting the current purchase, what is being purchased, ifadditional purchases can be made, if other errands close to the merchantcan be run, etc. Thus, embodiments of the invention allow differentpersons using the same payment account to easily communicate with eachother, substantially contemporaneously with a transaction beingconducted.

It should be understood that the present invention as described abovecan be implemented in the form of control logic using computer softwarein a modular or integrated manner. Based on the disclosure and teachingsprovided herein, a person of ordinary skill in the art will know andappreciate other ways and/or methods to implement the present inventionusing hardware and a combination of hardware and software.

Any of the software components or functions described in thisapplication, may be implemented as software code to be executed by aprocessor using any suitable computer language such as, for example,Java, C++ or Perl using, for example, conventional or object-orientedtechniques. The software code may be stored as a series of instructions,or commands on a computer readable medium, such as a random accessmemory (RAM), a read only memory (ROM), a magnetic medium such as ahard-drive or a floppy disk, or an optical medium such as a CD-ROM. Anysuch computer readable medium may reside on or within a singlecomputational apparatus, and may be present on or within differentcomputational apparatuses within a system or network.

The above description is illustrative and is not restrictive. Manyvariations of the invention will become apparent to those skilled in theart upon review of the disclosure. The scope of the invention can,therefore, be determined not with reference to the above description,but instead can be determined with reference to the pending claims alongwith their full scope or equivalents.

One or more features from any embodiment may be combined with one ormore features of any other embodiment without departing from the scopeof the invention.

A recitation of “a”, “an” or “the” is intended to mean “one or more”unless specifically indicated to the contrary.

What is claimed is:
 1. A method comprising: receiving, by a transactionprocessing server computer, a transaction authorization request messagefor a transaction conducted using a payment account of an accountholder; transmitting, by the transaction processing server computer,transaction data for the transaction to a notification server computer;transmitting, by the transaction processing server computer, thetransaction authorization request message to an issuer of the paymentaccount to process the transaction; while the issuer processes thetransaction to determine whether the transaction is authorized:determining, by the notification server computer, that a contact alertmessage is requested by comparing the transaction data to alertpreference data associated with the payment account; determining, by thenotification server computer, a communication channel and contactinformation for an account holder notification device operated by theaccount holder identified in the alert preference data associated withthe payment account for transmitting the contact alert message;generating, by the notification server computer, the contact alertmessage using the transaction data and the alert preference data,wherein the contact alert message comprises contact information of auser notification device used by a person conducting the transaction;and sending, by the notification server computer, the contact alertmessage comprising the contact information of the user notificationdevice to the account holder notification device, wherein the contactinformation of the user notification device is in form of an active linkon the account holder notification device, such that, when selected,automatically contacts the user notification device.
 2. The method ofclaim 1, further comprising: accessing, by the transaction processingserver computer, an enrollment database storing information associatedwith the payment account to determine that the payment account isenrolled in an alert messaging service.
 3. The method of claim 2,further comprising: retrieving, by the notification server computer,contact information for the account holder from a contact informationdatabase storing the contact information, wherein the account holdernotification device is accessible using the contact information of theaccount holder, wherein data stored at the contact information databaseis synchronized with data stored at the enrollment database.
 4. Themethod of claim 1 wherein the alert preference data comprises one ormore user profiles.
 5. The method of claim 1 wherein the usernotification device is a mobile phone, and wherein the method furthercomprises: activating the active link on the account holder notificationdevice; and automatically contacting the user notification device by theaccount holder notification device in response to activating the activelink.
 6. The method of claim 1 wherein the transaction processing servercomputer and the notification server computer are operated by a sameentity.
 7. The method of claim 1 wherein the contact information istranslated into a language that is understood by the account holder. 8.The method of claim 1 wherein the person conducting the transaction isdifferent from the account holder.
 9. The method of claim 1, furthercomprising: generating, by the notification server computer, a generalalert message in addition to the contact alert message; and sending thegeneral alert message to the user notification device used by the personconducting the transaction.
 10. The method of claim 1, wherein thecontact information comprises a phone number or an email address.
 11. Acontact alert system comprising: an alert database comprising alertpreference data; a notification server computer coupled to the alertdatabase, the notification server computer comprising a first processorand a first computer-readable medium coupled to the first processor; anda transaction processing computer coupled to the notification servercomputer, the transaction processing computer comprising a secondprocessor and a second computer-readable medium coupled to the secondprocessor, the second computer-readable medium comprising instructionsthat, when executed by the second processor, cause the second processorto: receive a transaction authorization request message for atransaction conducted using a payment account of an account holder;transmit transaction data for the transaction to the notification servercomputer; transmit the transaction authorization request message to anissuer of the payment account to process the transaction; while theissuer processes the transaction to determine whether the transaction isauthorized, the first computer-readable medium comprising instructionsthat, when executed by the first processor, cause the first processorto: determine that a contact alert message is requested by comparing thetransaction data to alert preference data associated with the paymentaccount; determine a communication channel and contact information foran account holder notification device operated by the account holderidentified in the alert preference data associated with the paymentaccount for transmitting the contact alert message; generate the contactalert message using the transaction data and the alert preference data,wherein the contact alert message comprises contact information of auser notification device used by a person conducting the transaction;and send the contact alert message comprising the contact information ofthe user notification device to the account holder notification device,wherein the contact information of the user notification device is inform of an active link on the account holder notification device, suchthat, when selected, automatically contacts the user notificationdevice.
 12. The contact alert system of claim 11, further comprising: anenrollment database storing information associated with the paymentaccount, wherein the second computer-readable medium further comprisinginstructions that, when executed by the second processor, cause thesecond processor to: access the enrollment database storing informationassociated with the payment account to determine that the paymentaccount is enrolled in an alert messaging service.
 13. The contact alertsystem of claim 12, wherein the first computer-readable medium furthercomprises instructions that, when executed by the first processor, causethe first processor to: retrieve contact information for the accountholder from a contact information database storing the contactinformation, wherein the account holder notification device isaccessible using the contact information of the account holder, whereindata stored at the contact information database is synchronized withdata stored at the enrollment database.
 14. The contact alert system ofclaim 11 wherein the alert preference data comprises one or more userprofiles.
 15. The contact alert system of claim 11 wherein when theactive link on the account holder notification device is activated, theuser notification device is automatically contacted by the accountholder notification device in response to activating the active link.16. The contact alert system of claim 11 wherein the transactionprocessing computer and the notification server computer are operated bya same entity.
 17. The contact alert system of claim 11 wherein thecontact information is translated into a language that is understood bythe account holder.
 18. The contact alert system of claim 11 wherein theperson conducting the transaction is different from the account holder.19. The contact alert system of claim 11, wherein the firstcomputer-readable medium further comprising instructions that, whenexecuted by the first processor, cause the first processor to: generatea general alert message in addition to the contact alert message; andsend the general alert message to the user notification device used bythe person conducting the transaction.
 20. The contact alert system ofclaim 11, wherein the contact information comprises a phone number or anemail address.